The application must ensure messages are encrypted when the SessionIndex is tied to privacy data.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-222406 | APSC-DV-000260 | SV-222406r508029_rule | Medium |
| Description |
|---|
| When the SessionIndex is tied to privacy data (e.g., attributes containing privacy data) the message should be encrypted. If the message is not encrypted there is the possibility of compromise of privacy data. |
| STIG | Date |
|---|---|
| Application Security and Development Security Technical Implementation Guide | 2020-09-30 |
Details
| Check Text ( C-24076r493126_chk ) |
|---|
| Ask the application representative for the design document. Review the design document for web services using SAML assertions. If the application does not utilize SAML assertions, this check is not applicable. Examine the contents of a SOAP message using a SessionIndex in the SAML element AuthnStatement. Verify the information which is tied to the SessionIndex. If the SessionIndex is tied to privacy information, and it is not encrypted, this is a finding. |
| Fix Text (F-24065r493127_fix) |
|---|
| Encrypt messages when the SessionIndex is tied to privacy data. |